The Silent Retirement Crisis: What Walks Out the Door When Your Most Experienced Operator Leaves
π 8 min read
Ontario's water sector is facing a wave of retirements β and most of what's at risk isn't written down anywhere. It's the instinct for when a pump "sounds off," the informal workaround for a finicky valve, the judgment calls that only come from decades on-site. This post looks at why documentation alone doesn't solve this problem, and what actually does.
In this post, you'll learn:
Why traditional documentation captures maybe 20% of what experienced operators actually know
The difference between mentoring and simply "shadowing" β and why most utilities only do the latter
A practical starting point for utilities with no formal knowledge transfer process at all
How to start this conversation with senior staff without it feeling like a countdown to their exit
Relevant for: Utility managers planning succession, senior operators nearing retirement, CAOs building workforce risk plans
The Knowledge That Was Never Written Down
Every experienced operator carries a body of knowledge that exists almost entirely outside of any manual or SOP. The particular sound a pump makes right before it needs attention. The informal workaround for a valve that's been "acting up" for years and is on next year's replacement list, but not this year's. The judgment call about when a reading that's technically within range still warrants a second look.
None of this is written down anywhere, and it's not because anyone was careless. It's because this kind of knowledge is genuinely difficult to document β it's built from thousands of small experiences accumulated over years, and it often doesn't fully surface until the exact moment it's needed.
Why Documentation Alone Doesn't Solve This
The instinctive response to this problem is "let's get it written down before they leave." That's a reasonable instinct, and documentation absolutely has value. But it captures a smaller portion of what's actually at risk than most people expect.
Documentation is good at capturing procedures β the steps, the sequence, the technical specifications. It's poor at capturing judgment β the "why" behind a decision, the pattern recognition built from years of small anomalies, the instinct for when something is off before there's a clear reading confirming it.
You can document that a certain valve requires extra attention. You can't fully document the accumulated sense, built over a decade, of exactly how much attention, under exactly what conditions, based on exactly what subtle signs.
Mentoring vs. Shadowing β And Why Most Utilities Only Do the Latter
Many utilities believe they're doing knowledge transfer because newer staff shadow experienced operators. Shadowing has value, but it's passive by design β the newer employee observes, and observation alone rarely transfers the deeper judgment underneath the visible action.
Mentoring is different, and more demanding, because it requires the experienced operator to narrate their own thinking, not just perform the task. That's a skill in itself β many excellent operators have never been asked to explain their instincts out loud, and doing so effectively often needs to be taught, not assumed.
Real mentoring includes deliberately walking through "why did you check that," "what made you notice that reading was off," and "what would have happened if we hadn't caught it." This is a fundamentally different β and more valuable β activity than simply working alongside someone.
Where to Start If You Have No Formal Process at All
Many small and mid-sized utilities have no structured knowledge transfer process whatsoever β it happens informally, if at all, and often only in the final weeks before someone leaves, when it's too rushed to be effective.
A realistic starting point doesn't require a large program. It requires:
Identifying the highest-risk knowledge first. Not everything an experienced operator knows is equally critical. Start with the judgment calls that, if lost, would create real operational or compliance risk β not the full breadth of everything they know.
Building in structured time, not hoping it happens informally. "They'll pick it up naturally" is how this knowledge is most commonly lost. A scheduled, protected hour a week for structured knowledge-sharing conversations accomplishes more than years of incidental proximity.
Starting well before the retirement date is set. The best knowledge transfer happens over 12-18 months, not the final two weeks of someone's tenure. If your utility doesn't yet know who's planning to retire in the next two years, that's the very first conversation to have.
Starting the Conversation Without It Feeling Like a Countdown
Supervisors are often hesitant to raise succession planning with senior staff, worried it will feel like being pushed out the door. Framed well, it doesn't have to.
The more effective framing isn't "you're leaving soon, so let's capture what you know." It's "what you know is valuable enough that we want to make sure it doesn't disappear β and we'd like your help figuring out the best way to pass it on." That framing positions the senior operator as a valued expert being asked to contribute their legacy, not someone being managed out.
The Real Cost of Getting This Wrong
The cost of inadequate knowledge transfer rarely shows up immediately. It shows up 8 months later, when a situation arises that the departed operator would have recognized instantly, and the newer staff member is troubleshooting from scratch β sometimes under real operational or compliance pressure.
That's the actual risk being managed here β not simply "who will do the job," but "will the person doing the job have the judgment that took years to build, or will they have to rebuild it the hard way, in real time, when it matters most."